Skip to content

docs: Document Authorization: Bearer for HTTP API auth#1746

Merged
lukekim merged 1 commit into
trunkfrom
docs/auth-bearer-http
May 19, 2026
Merged

docs: Document Authorization: Bearer for HTTP API auth#1746
lukekim merged 1 commit into
trunkfrom
docs/auth-bearer-http

Conversation

@claudespice
Copy link
Copy Markdown
Collaborator

Summary

Documents the new Authorization: Bearer ${api_key} header support for HTTP API authentication added in spiceai/spiceai#10911. Previously the docs only mentioned the X-API-Key header for HTTP routes.

Source PRs

Changes

  • website/docs/api/auth/index.md — extend the HTTP section to note that either X-API-Key or Authorization: Bearer ${api_key} is accepted, with a curl example for the Bearer form.

Test plan

  • cd website && npm run build passes locally (Docusaurus throws on broken links and undefined frontmatter tags)
  • Verified examples work locally
  • Links are valid
  • Version references are correct

HTTP routes now accept the API key in either `X-API-Key` or
`Authorization: Bearer ${api_key}`. The Bearer scheme matching is
case-insensitive. When both headers are present `X-API-Key` takes
precedence.

Source: spiceai/spiceai#10911
@claudespice claudespice self-assigned this May 19, 2026
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 19, 2026

✅ Pull with Spice Passed

Passing checks:

  • ✅ Title meets minimum length requirement (10 characters)
  • ✅ Has at least one of the required labels: area/blog, area/docs, area/cookbook, dependencies
  • ✅ No banned labels detected
  • ✅ Has at least one assignee: claudespice

@github-actions
Copy link
Copy Markdown

🚀 deployed to https://f74182c6.spiceai-org-website.pages.dev

@lukekim lukekim merged commit 6ffc124 into trunk May 19, 2026
6 of 8 checks passed
@lukekim lukekim deleted the docs/auth-bearer-http branch May 19, 2026 16:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants